Skip to content

ci: use RELEASE_TOKEN PAT for release workflow#2

Merged
stevensacks merged 1 commit intomainfrom
ci/release-token
Apr 27, 2026
Merged

ci: use RELEASE_TOKEN PAT for release workflow#2
stevensacks merged 1 commit intomainfrom
ci/release-token

Conversation

@stevensacks
Copy link
Copy Markdown
Contributor

Summary

Swaps secrets.GITHUB_TOKEN for secrets.RELEASE_TOKEN on actions/checkout and the changesets/action env in .github/workflows/release.yml.

Why

PRs created by workflows authenticated with the default GITHUB_TOKEN don't trigger downstream pull_request events (GitHub's recursion guard). That means the required build status check from ci.yml never runs on the auto-generated "chore: version packages" PR, and the PR can't be merged.

A fine-grained PAT acts like a real user, so PRs it creates trigger CI normally.

Setup required

Repo secret RELEASE_TOKEN must be set to a fine-grained PAT scoped to gaia-react/lint with: Contents R/W, Pull requests R/W, Workflows R/W.

🤖 Generated with Claude Code

Swaps secrets.GITHUB_TOKEN for secrets.RELEASE_TOKEN on actions/checkout
and the changesets/action env. PRs created with GITHUB_TOKEN don't
trigger downstream workflows (GitHub's recursion guard); using a PAT
restores normal pull_request CI triggering.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@stevensacks stevensacks merged commit dda0580 into main Apr 27, 2026
1 check passed
@stevensacks stevensacks deleted the ci/release-token branch April 27, 2026 13:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant